Summary

Replace basis-points-encoded fees (feeBps) with an absolute feeAmount (in raw token units) on capture() and charge(). The payer-approved minFeeBps / maxFeeBps on PaymentInfo are unchanged and continue to bound the fee, but they are now applied to the operator-supplied absolute amount rather than used to compute it:

minFee = amount * minFeeBps / 10_000
maxFee = amount * maxFeeBps / 10_000
require(minFee <= feeAmount <= maxFee)

This lets operators pass cent-aligned fees computed off-chain without losing precision to on-chain BPS truncation, while preserving the same payer-side guarantees.

Design doc: https://docs.google.com/document/d/1RCIXH0Q46XcwyYcu3027g9bKXHljrEX-y_ciBIdGNIQ

Implementation follows the approach used in PPS.

Changes

Contracts

• AuthCaptureEscrow.capture(...) and charge(...): uint16 feeBps → uint256 feeAmount.
• _validateFee now takes amount + absolute feeAmount and checks it against the min/max bounds derived from bps.
• _distributeTokens uses the supplied feeAmount directly (no on-chain multiplication/division).
• Error FeeBpsOutOfRange(feeBps, minFeeBps, maxFeeBps) → FeeAmountOutOfRange(feeAmount, minFee, maxFee).
• PaymentCharged / PaymentCaptured events: uint16 feeBps → uint256 feeAmount.
• Collector call sites (ERC3009PaymentCollector, Permit2PaymentCollector) updated to the new signature.

Docs

• docs/Fees.md, docs/operations/Capture.md, docs/operations/Charge.md rewritten to describe absolute-fee semantics with worked examples and updated error list.

Tooling

• Added [profile.ci] to foundry.toml.

Testing

Tests updated across the suite to pass absolute feeAmount values instead of bps:

• test/src/PaymentEscrow/{authorize,capture,charge,refund,reentrancy,e2eCoinbaseSmartWallet}.t.sol
• test/src/collectors/SpendPermissionPaymentCollector.t.sol
• test/gas/gasBenchmark.t.sol
• test/base/AuthCaptureEscrowBase.sol, test/base/AuthCaptureEscrowSmartWalletBase.sol

FeeAmountOutOfRange bounds cases (below-min, above-max, and both-zero) are exercised in capture.t.sol / charge.t.sol.

Backwards compatibility

Breaking public ABI change: charge(), capture(), PaymentCharged, and PaymentCaptured all change parameter/field types. Integrators must migrate before upgrading.